Distributed scheduling of media channel playout

ABSTRACT

Multiple scheduling producers such as content management systems, advertisement systems, and emergency broadcast systems can independently send scheduling events to scheduling consumers such as streaming servers, guide generators, and playlogs. The scheduling consumers maintain state machines with persistent storage to process scheduling events from scheduling producers and output media channel playlists, channel guides, and/or content. Scheduling producers can contribute independently to define a channel playout while information at scheduling consumers remains synchronized.

CROSS REFERENCE TO RELATED PATENT APPLICATION

This application claims priority and is a continuation of U.S. patentapplication Ser. No. 14/489,442, entitled “DISTRIBUTED SCHEDULING OFMEDIA CHANNEL PLAYOUT,” filed Sep. 17, 2014, which is a continuation ofU.S. patent application Ser. No. 12/353,922, entitled “DISTRIBUTEDSCHEDULING OF MEDIA CHANNEL PLAYOUT,” filed Jan. 14, 2009, all of whichis incorporated herein by this reference in its entirety for allpurposes.

TECHNICAL FIELD

The present disclosure relates to scheduling of content for mediachannel playout.

DESCRIPTION OF RELATED ART

A media channel includes multiple pieces of media such as video clipsand advertisements stitched together to create a continuous, linear flowof content. Examples of content include video clips, television shows,songs, advertisements, etc. However, conventional mechanisms forstitching multiple pieces of media together are limited. In manyinstances, conventional mechanisms lack flexibility and manageability.

Consequently, it is desirable to provide improved techniques andmechanisms for scheduling content.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may best be understood by reference to the followingdescription taken in conjunction with the accompanying drawings, whichillustrate particular embodiments.

FIG. 1 illustrates one example of a system for scheduling content.

FIG. 2 illustrates one example of a distributed system for schedulingcontent for media channel playout.

FIG. 3 illustrates one example of a scheduling event.

FIG. 4 illustrates one example of clip management.

FIG. 5 illustrates one example of operation of a consumer of schedulingevents.

FIG. 6 illustrates one example of streaming server system.

FIG. 7 illustrates one example of a streaming server.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Reference will now be made in detail to some specific examples of theinvention including the best modes contemplated by the inventors forcarrying out the invention. Examples of these specific embodiments areillustrated in the accompanying drawings. While the invention isdescribed in conjunction with these specific embodiments, it will beunderstood that it is not intended to limit the invention to thedescribed embodiments. On the contrary, it is intended to coveralternatives, modifications, and equivalents as may be included withinthe spirit and scope of the invention as defined by the appended claims.

For example, the techniques of the present invention will be describedin the context of state machines. However, it should be noted that thetechniques of the present invention be applied using a variety ofmechanisms. In the following description, numerous specific details areset forth in order to provide a thorough understanding of the presentinvention. Particular example embodiments of the present invention maybe implemented without some or all of these specific details. In otherinstances, well known process operations have not been described indetail in order not to unnecessarily obscure the present invention.

Various techniques and mechanisms of the present invention willsometimes be described in singular form for clarity. However, it shouldbe noted that some embodiments include multiple iterations of atechnique or multiple instantiations of a mechanism unless notedotherwise. For example, a system uses a processor in a variety ofcontexts. However, it will be appreciated that a system can use multipleprocessors while remaining within the scope of the present inventionunless otherwise noted. Furthermore, the techniques and mechanisms ofthe present invention will sometimes describe a connection between twoentities. It should be noted that a connection between two entities doesnot necessarily mean a direct, unimpeded connection, as a variety ofother entities may reside between the two entities. For example, aprocessor may be connected to memory, but it will be appreciated that avariety of bridges and controllers may reside between the processor andmemory. Consequently, a connection does not necessarily mean a direct,unimpeded connection unless otherwise noted.

Overview

Multiple scheduling producers such as content management systems,advertisement systems, and emergency broadcast systems can independentlysend scheduling events to scheduling consumers such as streamingservers, guide generators, and playlogs. The scheduling consumersmaintain state machines with persistent storage to process schedulingevents from scheduling producers and output media channel playlists,channel guides, and/or content. Scheduling producers can contributeindependently to define a channel playout while information atscheduling consumers remains synchronized.

Example Embodiments

A media channel is generated by stitching individual pieces of contenttogether to create a continuous linear flow of content, referred toherein as a “playout”. Examples of content include video clips,television shows, songs, advertisements, emergency broadcast messages,looping playlists of content, etc. Content providers need a way toefficiently manage content in a flexible and dynamic manner. Accordingto various embodiments, content providers need to schedule the startingand/or ending times for content programs, insert advertisements, addfiller into blank spaces between content, cut between content programs,preempt currently scheduled content for higher priority content, etc.

A scheduler is a system that receives content and schedule informationspecified by the content providers and determines the playout for eachchannel. In many instances, the playout is expressed as a timed sequenceof programs.

According to various embodiments, a system is provided to allow anynumber of scheduling producers such as content provider and contentmanagement systems, advertising systems, and emergency broadcast systemsthe ability to independently contribute to a channel schedule. Thesystem composites content to produce a single playout for the channel.For example, one scheduling producer might contribute regularlyscheduled programming, while a second producer contributes theadvertisements that should be inserted, and a third producer contributespreemptive emergency programming. In some examples, scheduling producersprovide time stamped scheduling events to scheduling consumers.

According to various embodiments, a content provider (CP) accesses acontent management system (CMS) and modifies a playlist for a particularchannel. In particular embodiments, the content provider accesses acontent management system and schedules a playlist for some channel tostart looping at a particular time in the future. In other embodiments,the content provider accesses the content management system andrestricts availability of a clip at some time interval in the future asa clip finishes transcoding at the content management system. In stillother embodiments, an advertising system selects an advertising clip forinsertion into the next available advertising slot in some channel.

Scheduling events are conveyed to scheduling consumers using a messagingservice such as Java Messaging Service (JMS). The messaging servicereliably transmits messages between two components. Scheduling eventsmay identify playlists, content identifiers, timing information,actions, etc. Scheduling producers independently transmit schedulingevents to scheduling consumers.

According to various embodiments, there are any number of schedulingconsumers. Examples of scheduling consumers include guide generatorsthat create continuously updated channel guides, playlogs that maintaina database of entire clip sequences played out for each channel, contentprovider management systems that allow content providers to analyzeplayout of content and advertisements, and streaming servers that usescheduling events to send clips to individual client devices such asmobile phones and computer systems. Each scheduling consumer can lookahead to see what programming is coming up and, if necessary, continueto play out the channel even if the scheduling consumer loses networkconnectivity to receive further incoming schedule data.

In particular embodiments, each scheduling consumer has a state machine(SM) that turns the stream of scheduling events into a playout for eachchannel. A playout is a timestamped sequence of clips that should playout for that particular channel. In particular embodiments, the statemachine maintains a variety of data structures in persistent storage.According to various embodiments, the state machine maintainsinformation about the available playlists, when/how each playlist isscheduled to play, and the availability interval of each clip in aplaylist. The state machine state also includes a timestamped “playhead”for each channel representing a point in time during the channel'splayout. The state machine also recognizes the point in time when oneclip in a channel playout will end and the next one should begin.

According to various embodiments, the state machine consumes schedulingevents in chronological order, modifies state variables in response tothose scheduling events, and outputs the sequence of clips for eachchannel. In some examples, the state machine prioritizes schedulingevents. According to various embodiments, the system beneficially allowsmultiple scheduling consumers to unroll each channel into identicalplayouts. According to various embodiments, each scheduling event ispost-timestamped by a commitment interval chosen to be long enough toexceed the latency of the scheduling event delivery mechanism. Secondly,an SM that falls behind, for example due system or network failure, willdetect this when it receives the first out-of-order scheduling event, atwhich point it will resynchronize itself. Finally, a scheduling consumerthat needs to synchronize itself either because it is starting up forthe first time or because it experienced an outage, can initializeitself by copying the state machine state from any other state machineavailable on the network.

A benefit to this model of clip scheduling is that any schedulingconsumer, at any time, is able to look ahead in order to approximate achannel playout out to a time arbitrarily far in the future. Thisprovides both functionality and fault-tolerance. In particularembodiments, a guide generator can determine what is going to play forthe next 24 hours and show that schedule to an end-user, barringunforeseen events such as a content provider making a late-breakingschedule change or an emergency broadcast preempting a regularlyscheduled program. In another example, a streaming server can continueto play out all channels even if it becomes temporarily unable toreceive new scheduling events.

Another benefit is that the model permits multiple scheduling producersto contribute independently to define a channel's playout. For example,an asset management system could be designed as a single schedulingproducer responsible only for clip uploads. Separately, a contentprovider might interact with a content management system user interfacethat would operate as a second scheduling producer to define playlistsand schedule them for playout. An advertising server might operate as athird scheduling event producer that inserts advertisements into achannel without knowing any details about how the content provider hasscheduled the playlists for that channel. The state machine semanticsare designed to permit this kind of distributed schedule compositing inorder to allow independent contribution.

For example, the content provider does not need to know when theadvertising breaks are, or for how long, and by the same token theadvertising server does not need to know what the non-advertising clipsare or how they are scheduled for playout.

According to various embodiments, preemptive scheduling is also allowed.An emergency broadcast or late-breaking news item could preempt acurrently scheduled program. A set of scheduling events for thepreemptive content could be sent out in real time to interrupt currentlyscheduled content. When the emergency broadcast or late-breaking newsprogram is over, the system can automatically fall back to the regularlyscheduled programming.

FIG. 1 is a diagrammatic representation illustrating one example of aclip distribution system. According to various embodiments, a clipserver 101 receives video clips 111, playlist definitions 113, andplaylist schedules 115 from various content sources. In particularembodiments, playlist definitions 113 identify a number of clipsincluded in various playlists. Playlist schedules 115 indicate that aplaylist will loop at a particular time. The clip server sends clipssuch as video clips to a storage area network 121. Playlist schedulesand definitions are sent to a metadata database 123. A playlistbroadcaster 125 accesses the metadata database 123 to write files to astreaming server 131. In particular embodiments, the files direct astreaming server to play clip A at 5:00, clip B at 5:01, clip C at 5:03,etc. The streaming server 131 then accesses the storage area network 121to obtain clips A, B, and C.

However, this architecture provides limited ability for contentproviders to manage content or change content. For example, if a contentprovider decides to provide alternate programming at 5:01, it can noteasily convey this to the streaming server 131.

Content from various sources can also not easily be aggregated.Advertising can not easily be inserted into a playout withoutintervention by a content provider. Furthermore, if the streaming server131 loses a connection with the playlist broadcaster 125, the streamingserver 131 is unable to determine what to play next.

Consequently, a system is provided to allow any number of schedulingproducers such as content providers, content management systems,advertising systems, and emergency broadcast systems to independentlymanage scheduling provided to multiple scheduling consumers such asstreaming servers, guide generators, content provider managementsystems, playlogs, etc.

FIG. 2 illustrates one example of a system having multiple schedulingproducers independently managing schedules provided to multiplescheduling consumers. According to various embodiments, schedulingproducers 241 include content management system 201, advertisementsystem 203, and emergency broadcast system 205. In particularembodiments, scheduling producers are timestamped schedule event (TSE)producers. According to various embodiments, a content provider sendsclips 211, clip management messages 213, and playlist managementmessages 215 to a content management system 201. Clips 211 may includevideo clips, songs, messages, television shows, etc. Clip managementmessages 213 may indicate when a clip should be made available. Playlistmanagement messages 215 may indicate how to create, modify, or delete aplaylist or when to schedule playout. Each scheduling event may be usedto update an existing schedule at a scheduling consumer.

An advertiser can send advertisements 221, advertisement managementmessages 223, and advertisement playout management messages 225 to anadvertisement system 203. Advertisement management messages 223 andadvertisement playout management messages 225 may include rulesindicating that advertisements should be played a particular number oftimes at a specific time period. According to various embodiments,public agencies send emergency messages 231 and emergency messagemanagement instructions 233 to an emergency broadcast system 205. Theemergency message management instructions 233 may direct schedulingconsumers to repeat emergency messages a certain number of times.

Scheduling event messaging middleware 245 reliably sends schedulingevents such as timestamped schedule events (TSEs) to schedulingconsumers. According to various embodiments, the scheduling eventmessaging middleware 245 uses Java Messaging Service (JMS). Schedulingevents may include playlists, content identifiers, timing information,actions, etc. The scheduling events are transmitted to schedulingconsumers 243. According to various embodiments, scheduling consumersinclude streaming server 251, guide generator/content providermanagement tool 253, and playlog 255. According to various embodiments,streaming server 251 includes a state machine with a persistent store261 that is continuously updated as scheduling events are received. Thestate machine 261 has logic for prioritizing scheduling events anddynamically modifying output as scheduling events are received.According to various embodiments, the streaming server 251 also hasaccessed to a storage area network to transmit clips corresponding toscheduling events.

A guide generator/content provider management tool 253 also has a statemachine with a persistent store 263. The guide generator/contentprovider management tool 253 receives scheduling events to providecontinuously updated guides. Instead of having static guides generatedby content providers, the guide generator/content provider managementtool 253 can provide continuously updated guides that can includeinformation on advertisements, breaking news, emergency broadcastmessages, as well other clip content. Content providers can analyzeguide generator 253 output to determine not only when content wasplayed, but what commercials were interspersed and what messages mayhave interrupted the content. A playlog 255 also includes a statemachine with a persistent store 265.

According to various embodiments, the state machines 261, 263, and 265all have the same logic and the same state and may be used tosynchronize each other. In some examples, minor variations in state mayoccur temporarily, but it is recognized that minor variations in statedo not significantly impact system performance. A playlog 255 maintainsa full listing of playout content for review and analysis. According tovarious embodiments, the state machines 261, 263, and 265 outputplaylists indicating that clip A should be played at 5:00, clip B shouldbe played at 5:30, etc. If a streaming server 251 loses a connectionwith the messaging middleware 245, the streaming server 251 can stillplay clips using its existing state information. In particularembodiments, new TSEs are received continuously, and guides and playlogsare updated continuously.

FIG. 3 illustrates one example of a scheduling event. According tovarious embodiments, scheduling events such as TSEs are reliablytransmitted from scheduling producers to scheduling consumers. Inparticular embodiments, the scheduling events include information formanaging clips, playlists, and characteristics associated with clips andplaylists. A variety of scheduling event formats can be used. Accordingto various embodiments, a scheduling event 301 includes a playlist 311.The playlist 311 includes playlist entry 321 and playlist entry 331.Playlist entry 321 includes clip ID 323, clip info 325, duration 327, aswell as a time interval 329 when the entry 321 should be played.Playlist entry 331 includes clip ID 333, clip info 335, duration 337,and a time interval 339 when the entry 331 should be played. Inparticular embodiments, the scheduling event 301 also includes aplaylist instruction 351 such as initiating play of the playlist. Thechannel ID 353 identifies a channel associated with the scheduling event301. The schedule ID 355 depicts the schedule. The time interval 357indicates when a particular playlist 311 should be played. Recurrence359 directs a scheduling consumer to repeat a particular piece ofcontent. According to various embodiments, a source identifier 361 isalso provided to identify the source of the scheduling event. The sourceidentifier 361 may be evaluated when prioritizing scheduling events.

FIG. 4 illustrates one example of clip management. According to variousembodiments, state machines associated with various scheduling consumershave semantics of preemption. In available implementations, clips do notbegin to play until a previous clip has finished playing. By contrast,the techniques of the present invention allow new clips to preemptexisting clips if necessary. Alternatively, new clips may still bedelayed until prior clips have finished playing. A playout 431 includesclip 401, 403, and 405. According to various embodiments, a clip 401 maybe a television show while clips 403 and 405 may be advertisements. Inone implementation, a clip 403 is scheduled to begin playing while aclip 401 is still playing. However, the clip 403 is delayed until clip401 completes playing. With preemption, a clip 413 interrupts a showincluding clips 411 and 417 and delays portion 417. A show is split intoclip 411 and 417 with intervening commercial clips 413 and 415 forplayout of content flow 433.

FIG. 5 illustrates one example of scheduling consumer operations. At501, a scheduling consumer obtains scheduling state from anotherscheduling consumer if available. According to various embodiments, thestate is obtained at startup or after system interruption. At 503,scheduling events are received from multiple scheduling producers. At505, scheduling events are prioritized. In some examples, TSEs fromparticular scheduling producers are given high priority while ones fromother scheduling producers are given low priority. In particularembodiments, emergency broadcast system TSEs are assigned the highestpriority while advertising is assigned the next highest priority.Various advertisers may also pay different rates to obtain differentpriority levels for their advertisements. At 507, playlists and clipordering are updated. According to various embodiments, state machinelogic is used to update playlists and clip ordering. At 509, clips areobtained from a storage area network as needed. At 511, data istransmitted to a client. Data may include program guides, playoutstreams, playlogs, etc.

FIG. 6 is a diagrammatic representation illustrating one example of asystem that can use the techniques and mechanisms of the presentinvention to send out data. According to various embodiments, streamingservers 619, 621, 623, and 625 are configured to provide media contentto a mobile device 601 using protocols such as RTP and RTCP. Although amobile device 601 is shown, it should be recognized that other devicessuch as set top boxes and computer systems can also be used. Inparticular examples, the streaming servers 619, 621, 623, and 625 canthemselves establish sessions with mobile devices and stream video andaudio content to mobile devices. However, it is recognized that in manyinstances, a separate controller such as controller 605 or controller607 can be used to perform session management using a protocol such asRTSP. It is recognized that streaming servers require the bulk of theprocessing power and resources used to provide media content mobiledevices.

By separating out content streaming and session management functions, acontroller can select a streaming server geographically close to amobile device 601. It is also easier to scale, as streaming servers andcontrollers can simply be added as needed without disrupting systemoperation. A load balancer 603 can provide further efficiency duringsession management using RTSP 633 by selecting a controller with lowlatency and high throughput.

According to various embodiments, the streaming servers 619, 621, 623,and 625 have access to a campaign server 643. The campaign server 643provides profile information for various mobile devices 601. In someexamples, the campaign server 643 is itself a streaming server or acontroller. The campaign server 643 can receive information fromexternal sources about devices such as mobile device 601. Theinformation can be profile information associated with various users ofthe mobile device including interests and background. The campaignserver 643 can also monitor the activity of various devices to gatherinformation about the devices. The streaming servers 619, 621, 623, and625 can obtain information about the various devices from the campaignserver 643. In particular examples, a streaming server 625 uses thecampaign server 643 to determine what type of media clips a user on amobile device 601 would be interested in viewing.

In one example, a mobile device 601 requests a particular stream. Acontroller 607 establishes a session with the mobile device 601 and thestreaming server 625 begins streaming the content to the mobile device601 using RTP 631. In particular examples, the streaming server 625obtains profile information from campaign server 643.

FIG. 7 illustrates one example of a streaming server. According toparticular embodiments, a system 700 suitable for implementingparticular embodiments of the present invention includes a processor701, a memory 703, an interface 711, and a bus 715 (e.g., a PCI bus orother interconnection fabric) and operates as a streaming server. Astate machine can be implemented using processor 701, memory 703, andsome form of persistent storage. When acting under the control ofappropriate software or firmware, the processor 701 is responsible formodifying and transmitting data to a client. Various speciallyconfigured devices can also be used in place of a processor 701 or inaddition to processor 701. The interface 711 is typically configured toend and receive data packets or data segments over a network.

Particular examples of interfaces supports include Ethernet interfaces,frame relay interfaces, cable interfaces, DSL interfaces, token ringinterfaces, and the like. In addition, various very high-speedinterfaces may be provided such as fast Ethernet interfaces, GigabitEthernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces,FDDI interfaces and the like. Generally, these interfaces may includeports appropriate for communication with the appropriate media. In somecases, they may also include an independent processor and, in someinstances, volatile RAM. The independent processors may control suchcommunications intensive tasks as packet switching, media control andmanagement.

According to various embodiments, the system 700 is a streaming server,a guide generator, a playlog system, or a content provider managementtool. The system 700 maintains a state machine synchronized with thestate of other scheduling consumers. The streaming server may alsoinclude a transceiver and streaming buffers. The content server may alsobe associated with subscription management, logging and reportgeneration, and monitoring capabilities. In particular embodiments,functionality for allowing operation with mobile devices such ascellular phones operating in a particular cellular network and providingsubscription management. According to various embodiments, anauthentication module verifies the identity of devices including mobiledevices. A logging and report generation module tracks mobile devicerequests and associated responses. A monitor system allows anadministrator to view usage patterns and system availability. Accordingto various embodiments, the content server 791 handles requests andresponses for media content related transactions while a separatestreaming server provides the actual media streams.

In the foregoing specification, the invention has been described withreference to specific embodiments. However, one of ordinary skill in theart appreciates that various modifications and changes can be madewithout departing from the scope of the invention as set forth in theclaims below. Accordingly, the specification and figures are to beregarded in an illustrative rather than a restrictive sense, and allsuch modifications are intended to be included within the scope ofinvention.

It is claimed:
 1. A method for distributed scheduling, the methodcomprising: receiving, at a scheduling event messaging middleware, aplurality of scheduling events and their associated time-stamps from aplurality of scheduling producers, wherein the plurality of schedulingproducers are separate devices connected to the scheduling eventmessaging middleware over a network and the scheduling event messagingmiddleware is configured to receive scheduling events from any number ofdifferent scheduling producers over the network; dynamicallyprioritizing the scheduling events in a prioritized order as they arereceived at the scheduling event messaging middleware, wherein thepriority is based on the context of the scheduling event; sending, fromthe scheduling event messaging middleware, the plurality of schedulingevents and their associated time-stamps in the prioritized order, thatwere received from the plurality of scheduling producers to a pluralityof scheduling consumers, wherein the scheduling event messagingmiddleware is further configured to send scheduling events and theirassociated time-stamps to any number of different scheduling consumers;wherein each of the plurality of scheduling consumers includes a statemachine that turns the plurality of scheduling events into playouts foreach channel in a plurality of channels, wherein each time-stampidentifies a time for a specific channel, from the plurality ofchannels, at which the specific channel is to play one or more of theplurality of scheduling events.
 2. The method of claim 1, wherein aplayout comprises a timestamped sequence of clips to be played out for aparticular channel.
 3. The method of claim 1, wherein each state machinemaintains a variety of data structures in persistent storage, thevariety of data structures maintaining one or more of the followinginformation about: playlists, when/how each playlist is scheduled toplay, and the availability interval of each clip in a playlist.
 4. Themethod of claim 1, wherein the plurality of scheduling events includeone or more of the following: playlists, content identifiers, timinginformation, and actions.
 5. The method of claim 1, wherein theplurality of scheduling producers includes one or more of the following:content providers, content management systems, advertising systems, andemergency broadcast systems.
 6. The method of claim 1, wherein theplurality of scheduling consumers includes one or more of the following:guide generators that create continuously updated channel guides,playlogs that maintain a database of entire clip sequences played outfor each channel, content provider management systems that allow contentproviders to analyze playout of content and advertisements, andstreaming servers that use scheduling events to send clips to individualclient devices.
 7. The method of claim 1, wherein each state machine issynchronized with other state machines.
 8. A system, comprising:processor; memory; and scheduling event messaging middleware configuredfor: receiving a plurality of scheduling events and their associatedtime-stamps from a plurality of scheduling producers, wherein theplurality of scheduling producers are separate devices connected to thescheduling event messaging middleware over a network and the schedulingevent messaging middleware is configured to receive scheduling eventsfrom any number of different scheduling producers over the network;dynamically prioritizing the scheduling events in a prioritized order asthey are received, wherein the priority is based on the context of thescheduling event; sending the plurality of scheduling events and theirassociated time-stamps in the prioritized order, that were received fromthe plurality of scheduling producers to a plurality of schedulingconsumers, wherein the scheduling event messaging middleware is furtherconfigured to send scheduling events and their associated time-stamps toany number of different scheduling consumers; wherein each of theplurality of scheduling consumers includes a state machine that turnsthe plurality of scheduling events into playouts for each channel in aplurality of channels, wherein each time-stamps identifies a time for aspecific channel, from the plurality of channels, at which the specificchannel is to play one or more of the plurality of scheduling events. 9.The system of claim 8, wherein a playout comprises a timestampedsequence of clips to be played out for a particular channel.
 10. Thesystem of claim 8, wherein each state machine maintains a variety ofdata structures in persistent storage, the variety of data structuresmaintaining one or more of the following information about: playlists,when/how each playlist is scheduled to play, and the availabilityinterval of each clip in a playlist.
 11. The system of claim 8, whereinthe plurality of scheduling events include one or more of the following:playlists, content identifiers, timing information, and actions.
 12. Thesystem of claim 8, wherein the plurality of scheduling producersincludes one or more of the following: content providers, contentmanagement systems, advertising systems, and emergency broadcastsystems.
 13. The system of claim 8, wherein the plurality of schedulingconsumers includes one or more of the following: guide generators thatcreate continuously updated channel guides, playlogs that maintain adatabase of entire clip sequences played out for each channel, contentprovider management systems that allow content providers to analyzeplayout of content and advertisements, and streaming servers that usescheduling events to send clips to individual client devices.
 14. Thesystem of claim 8, wherein each state machine is synchronized with otherstate machines.
 15. A non-transitory computer readable storage mediumcomprising instructions for executing a method, the method comprising:receiving, at a scheduling event messaging middleware, a plurality ofscheduling events and their associated time-stamps from a plurality ofscheduling producers, wherein the plurality of scheduling producers areseparate devices connected to the scheduling event messaging middlewareover a network and the scheduling event messaging middleware isconfigured to receive scheduling events from any number of differentscheduling producers over the network; dynamically prioritizing thescheduling events in a prioritized order as they are received at thescheduling event messaging middleware, wherein the priority is based onthe context of the scheduling event; sending, from the scheduling eventmessaging middleware, the plurality of scheduling events and theirassociated time-stamps in the prioritized order, that were received fromthe plurality of scheduling producers to a plurality of schedulingconsumers, wherein the scheduling event messaging middleware is furtherconfigured to send scheduling events and their associated time-stamps toany number of different scheduling consumers; wherein each of theplurality of scheduling consumers includes a state machine that turnsthe plurality of scheduling events into playouts for each channel in aplurality of channels, wherein each time-stamp identifies a time for aspecific channel, from the plurality of channels, at which the specificchannel is to play one or more of the plurality of scheduling events.16. The non-transitory computer readable storage medium of claim 15,wherein a playout comprises a timestamped sequence of clips to be playedout for a particular channel.
 17. The non-transitory computer readablestorage medium of claim 15, wherein each state machine maintains avariety of data structures in persistent storage, the variety of datastructures maintaining one or more of the following information about:playlists, when/how each playlist is scheduled to play, and theavailability interval of each clip in a playlist.
 18. The non-transitorycomputer readable storage medium of claim 15, wherein the plurality ofscheduling events include one or more of the following: playlists,content identifiers, timing information, and actions.
 19. Thenon-transitory computer readable storage medium of claim 15, wherein theplurality of scheduling producers includes one or more of the following:content providers, content management systems, advertising systems, andemergency broadcast systems.
 20. The non-transitory computer readablestorage medium of claim 15, wherein the plurality of schedulingconsumers includes one or more of the following: guide generators thatcreate continuously updated channel guides, playlogs that maintain adatabase of entire clip sequences played out for each channel, contentprovider management systems that allow content providers to analyzeplayout of content and advertisements, and streaming servers that usescheduling events to send clips to individual client devices.